get_organization

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get details', which implies a read operation, but it does not disclose what happens on missing resources, whether any authentication or campaign scoping is required, or what the response contains.

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 short sentence with no filler and is easy to parse. It is appropriately concise, though the minor grammatical error and lack of detail slightly reduce clarity.

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 absence of annotations and an output schema, the description is incomplete: it does not explain required parameter semantics, the meaning of 'details', or the shape of the returned object. An agent would have to infer most of the calling contract from the parameter names and tool name.

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 has 0% description coverage and the description adds no meaning for the two required parameters, campaignId and id. The parameter names are somewhat self-explanatory, but the description does not clarify that id identifies the organization or how campaignId scopes the lookup.

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 states a clear verb and resource: 'Get details of a organization'. The singular 'a organization' helps distinguish it from list_organisations and from create/update/delete variants, though it does not explicitly mention that retrieval is by ID or campaign-scoped.

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 given about when to use this tool versus alternatives like list_organisations or get_quest. The intended context is only implied by the 'get' verb and the resource name, with no explicit exclusions or routing guidance.

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