get_member

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds no further behavioral context such as output format, error handling, or the effect of the 'raw' parameter. It only restates that it fetches a member, which is already clear from the name and annotations.

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 that is front-loaded with the action and resource. It contains no redundant information and is appropriately sized for a simple fetch tool.

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?

The tool is simple with one required parameter and no output schema. The description adequately conveys the core purpose and identifier type, but it omits details about the 'raw' parameter and return structure. Given the lack of output schema and parameter descriptions, a bit more context would make it complete.

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%, so the description must compensate. It clarifies that 'member_id' is numeric, but the 'raw' parameter is entirely unexplained. The description only partially adds meaning to one of two parameters, leaving the other undefined.

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 verb 'Fetch' with a specific resource 'one member (publisher)' and the key identifier required ('numeric Crossref member id'). This distinguishes it from sibling tools like 'search_members' (for searching) and 'get_member_works' (for works), so the tool's purpose is unambiguous.

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 when to use this tool: when you have a specific numeric Crossref member ID and need that member's details. It does not explicitly mention alternatives like 'search_members' for finding IDs, but the phrase 'by numeric ... id' provides clear context and exclusion of search use cases.

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