teamleader_quotations_info

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Get', which implies a read operation, but it does not indicate what the response contains, whether an invalid id errors, or any authentication or rate-limit considerations. This is minimal behavioral transparency.

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 sentence with no unnecessary words. It is front-loaded with the verb and resource, making it highly efficient and readable. Every word contributes to the core meaning.

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 getter with one parameter and no output schema, the description is minimally adequate. It states what the tool does, but it does not elaborate on the return structure or any edge cases (e.g., missing quotation). Given the absence of an output schema, a bit more detail could improve completeness, though it is not severely lacking.

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?

The schema defines a single required 'id' parameter with no description. The description explicitly says 'by id', clarifying that the parameter is the quotation identifier. However, it provides no format constraints, examples, or additional context, so it only partially compensates for the 0% schema coverage.

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 'Get' and the resource 'a single quotation', explicitly narrowing scope to a single item by id. This distinguishes it from sibling tools like teamleader_quotations_list (multiple) and teamleader_quotations_create (creation).

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 implies usage when a specific quotation id is known, but it does not explicitly mention alternatives such as using the list tool for multiple quotations. The 'by id' qualifier provides some context, but there is no clear when-to-use versus when-not-to-use guidance.

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