inei_get_geography_profile

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must bear burden. It outlines what data is returned (key census indicators) but doesn't explicitly state it is read-only or disclose any potential side effects or permissions. Adequate but not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence serves a purpose; the description is front-loaded with the main action, followed by clear examples and guidance without redundancy. Bullet list for common IDs improves readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only one parameter and no output schema, the description covers what the tool returns, how to get the input, and common values. Missing explicit mention of hierarchy levels (department/province/district) from the first sentence, but later clarifies. Sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema describes the parameter structure, and the description adds value by explaining the ID format, source tools, and providing concrete examples of valid IDs, which enriches the semantic understanding beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific verb 'Get' and resource 'Census 2017 population profile', and distinguishes this tool from siblings like inei_get_departments by focusing on a single geography profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the user to provide 'id_geografia' from related tools and lists common department IDs, which guides correct usage. Not explicit about when not to use, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.