Get Org Collection

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

Annotations already declare readOnlyHint=true. Description adds that organizationId is optional and narrows lookup, but does not explain default behavior when omitted, error handling, or return format. Adds some context but far from comprehensive.

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?

Extremely concise: two sentences with no wasted words. Purpose is front-loaded. The CLI equivalent in parentheses adds useful context without clutter.

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 get-by-id tool with 2 parameters and readOnly annotation, the description is adequate. However, given sibling tools like 'keychain_get_collection', it would benefit from mentioning what differentiates this from that. No output schema but return value is likely the collection object, which is implied.

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 description coverage is 100%, so baseline is 3. Description merely paraphrases the schema's description for organizationId ('narrows lookup' vs 'disambiguate'). No additional semantic value beyond what schema already provides.

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?

Clearly states 'Get an organization collection by id' with a specific verb and resource. The 'organization collection' distinction differentiates it from sibling 'keychain_get_collection' for personal collections.

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?

Implies usage through description but does not explicitly state when to use this tool versus alternatives like 'keychain_get_collection' for non-org collections. No when-not-to-use or alternative guidance provided.

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