compras_obter_resource

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

The description fully discloses behavior: it returns raw content and metadata, describes the return format with a JSON example, and explicitly states that if the URI does not exist it returns `_erro` instead of propagating an exception. This covers all key behavioral traits beyond the schema.

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?

The description is front-loaded with the core purpose and then provides additional detail on return format and error behavior. Every sentence adds value. A small improvement could be removing the blank line at the start.

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 the tool has only one parameter and includes an output schema in its description, the description is complete. It covers what the tool does, how to use it, what it returns, and error handling. No gaps remain.

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 coverage is 100% and the description adds significant value by including a JSON example of the return value and explaining error handling. The parameter `uri` has a detailed description with examples of valid URIs, making it easy to use. The description of the output complements the 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 verb 'Lê' (reads) and the resource type 'MCP Resource pela URI'. It distinguishes itself from 'compras_listar_resources' by referencing it in the parameter description as the way to discover URIs. The description also explains the error handling behavior.

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?

The description explicitly says to use 'compras_listar_resources' to discover available URIs, providing clear guidance on how to prepare for this tool. It does not explicitly state when not to use it, but the purpose is narrow enough that misuse is unlikely.

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