Get Marvin resource

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

With no annotations, the description must disclose behavioral traits but only states the retrieval action. It does not mention idempotency, error handling (e.g., what happens if slug not found), or any side effects. The description does not contradict annotations but provides minimal insight beyond the core function.

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 a single, clear sentence with no wasted words. However, it could benefit from additional context while remaining concise, such as mentioning that the slug is unique or what the response contains.

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?

For a simple tool with one parameter and no annotations or output schema, the description covers the basic action and identifier. It lacks completeness in behavioral and usage details, which are important for an agent to invoke correctly. An ideal description would include typical error conditions and the nature of the resource.

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 0% (no property descriptions). The description adds only 'by slug', which implies the slug identifies the resource but does not clarify format, constraints, or role. It adds marginal value over the schema's parameter name and type.

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 'Get' and the specific resource 'one reusable Marvin resource' with the method 'by slug'. It effectively distinguishes from sibling tools like marvin_list_resources, which lists resources without specifying retrieval by slug.

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?

No guidance on when to use this tool versus alternatives. For example, it does not indicate that this tool is appropriate when a slug is known, while marvin_list_resources should be used to discover slugs. No exclusions or context provided.

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