Affiliates_Retrieveanaffiliate

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

With no annotations, the description must bear the full burden of behavioral disclosure. It only states 'Retrieve', implying a read operation, but does not explain pagination, filtering behavior, authentication requirements, or response format, despite the presence of 5 optional parameters.

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 extremely concise with a single phrase, and the key action is front-loaded. While it lacks detail, the brevity is acceptable for a simple tool, though more structure could be beneficial.

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 complexity of 5 optional parameters and no output schema, the description is too brief. It does not explain what an affiliate is, what data is returned, or how the parameters filter results, making it incomplete for effective tool use.

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?

Although schema description coverage is 100%, each parameter description is merely a placeholder like 'Query parameter: include'. The tool description adds no additional meaning beyond what the schema provides, leaving the agent without clarification on how these parameters affect the retrieval.

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 action 'Retrieve' and the resource 'an affiliate', making the basic purpose identifiable. However, it does not differentiate from the sibling tool 'Affiliates_Listallaffiliates', which likely retrieves multiple affiliates, leaving ambiguity about singular vs. list retrieval.

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 is provided on when to use this tool versus similar tools like Affiliates_Listallaffiliates. There is no mention of context, prerequisites, or alternatives, leaving the agent without decision-making support.

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