get_session_info

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

No annotations are present. The description claims to 'get information' implying idempotency and safety, but does not explicitly state side effects, permissions, or rate limits. For a tool with no annotations, more behavioral disclosure is needed.

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 short and front-loaded with the purpose. The docstring-style 'Args:' and 'Returns:' sections are standard but could be omitted for conciseness. Overall, it is efficient without wasting words.

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 a single parameter and the existence of an output schema (unseen), the description should clarify the scope of returned information. 'Dictionary containing session information' is vague; it does not specify what fields or overall purpose the session info serves, leaving gaps for the 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?

The description adds minimal value over the schema: 'session_id: ID of the session.' The schema already has the property name and type. No format, constraints, or examples are provided. Schema description coverage is 0%, so the description should compensate but does not.

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 verb 'Get' and resource 'information about a workflow session,' indicating a retrieval operation for a single session. While it distinguishes from siblings like 'list_sessions' by specifying a single session ID, it does not explicitly contrast with other tools.

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 provided on when to use this tool versus alternatives (e.g., list_sessions, start_workflow). The description lacks usage context, prerequisites, or exclusion criteria.

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