sdtm.get

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

No annotations exist; description says 'Get latest' but does not explain what 'latest' means, whether the call is idempotent, or any side effects. Minimal behavioral disclosure beyond the basic operation.

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?

Single sentence is concise and front-loaded, but it is under-specified. Could include more context without becoming verbose.

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. However, it lacks details on the meaning of 'latest' and the nature of the specialization, leaving gaps for an AI agent.

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 0%; the sole parameter datasetSpecializationId is not explained in the description. The parameter name is somewhat self-explanatory but the description adds no additional meaning or format guidance.

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?

Description clearly states the tool retrieves the latest SDTM specialization by its ID, using specific verb 'Get' and resource 'SDTM specialization'. However, it does not distinguish from sibling tools like sdtm.packages.getSpecialization or sdtm.list.

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 such as sdtm.list or sdtm.byBiomedicalConcept. No exclusions or prerequisites provided.

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